GH#1134: guard checkout editor generated CSS state#1135
Conversation
|
Warning Rate limit exceeded
To continue reviewing without waiting, purchase usage credits in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Completion Summary
|
6280f4a to
6f0e48d
Compare
🔨 Build Complete - Ready for Testing!📦 Download Build Artifact (Recommended)Download the zip build, upload to WordPress and test:
🌐 Test in WordPress Playground (Very Experimental)Click the link below to instantly test this PR in your browser - no installation needed! Login credentials: |
🔨 Build Complete - Ready for Testing!📦 Download Build Artifact (Recommended)Download the zip build, upload to WordPress and test:
🌐 Test in WordPress Playground (Very Experimental)Click the link below to instantly test this PR in your browser - no installation needed! Login credentials: |
|
Performance Test Results Performance test results for 8259ce4 are in 🛎️! Note: the numbers in parentheses show the difference to the previous (baseline) test run. Differences below 2% or 0.5 in absolute values are not shown. URL:
|
Completion Summary
Merged via PR #1135 to main. aidevops.sh v3.14.75 spent 1m on this as a headless bash routine. |
Completion Summary
Merged via PR #1135 to main. aidevops.sh v3.14.75 spent 1m on this as a headless bash routine. |
Closing SummaryWhat doneAdded regression coverage for the recovered checkout editor generated-CSS state. PR #1077 had already recovered and merged the valuable PR #1076 asset revert, so PR #1135 adds durable verification for #1134 without making further asset changes. Testing Evidence
Key decisions
Files changed
BlockersNone. Follow-upNone required. Released inMerged via PR #1135. aidevops.sh v3.14.75 plugin for OpenCode v1.14.33 with gpt-5.5 spent 19m and 208,781 tokens on this as a headless worker. |
…n phones (#1162) The mobile (<=782px) view of the checkout form editor had three usability defects that made the screen effectively unusable on phones: 1. The expanded-row layout for TYPE / SLUG / MOVE columns relied on WordPress core's responsive list-table CSS, which absolutely positions the data-colname label in a 32%-wide strip on the left of each cell. Inside the narrow checkout-editor postbox that strip is too thin and the label collapses to one character per line ('T..s it e_ ur l' instead of 'Type: site_url'), with the value text overlapping it. 2. The 'Add new Field' wubox modal used a 600px fixed pixel width set inline by wubox.js, overflowing the viewport on phones and clipping labels on both edges. 3. The field-type tile grid used wu-w-1/4 (4 columns), producing ~24vw tiles on phones — too narrow for labels like 'PASSWORD', 'TEMPLATES', and 'DOMAIN SELECTION'. Fixes: - Add a new @media (max-width: 782px) block to checkout-editor.css that switches the expanded-row layout to a stacked block layout (label on its own row above the value), hides the ORDER and MOVE columns, and stacks the postbox header and step action buttons vertically. - Bump the existing wubox responsive breakpoint in admin.css from 400px to 782px (the WordPress admin mobile breakpoint) and override the inline pixel width with width: 100vw !important so the modal fills the screen on phones. - Drop the field-type tile grid from 4 columns to 2 on mobile so each label has room to render. Production users load checkout-editor.min.css and admin.min.css, which are rebuilt only at release time. Per PR #1135, feature branches must not hand-edit the .min.css files. To ship the fix to production users immediately, the same @media block is also injected via wp_add_inline_style() from Checkout_Form_Edit_Admin_Page::register_scripts(). The source .css and inline-PHP copies cross-reference each other so they stay in sync. Tests: - Extends tests/unit/Checkout_Editor_Assets_Test.php (introduced in PR #1135) with a new test asserting the wp_add_inline_style call is wired up and contains the expected selectors and rules. The existing source-only guard remains intact: checkout-editor.min.css is not modified on this branch. Verified at 390x844 (collapsed, expanded, modal, per-field edit) and 1280x800 (5 columns, modal centered at 600px) — desktop unaffected.
Summary
assets/css/checkout-editor.csswhile guardingassets/css/checkout-editor.min.cssfrom the manually inlined PR Fix: Make checkout form editor fully functional on mobile #1073 block on feature branches.checkout-editor.min.cssis already in the expected pre-PR Fix: Make checkout form editor fully functional on mobile #1073 state onmain.Verification
vendor/bin/phpcs tests/unit/Checkout_Editor_Assets_Test.phpWP_TESTS_DIR=/tmp/wordpress-tests-lib vendor/bin/phpunit --filter Checkout_Editor_Assets_TestResolves #1134
Source PR: #1076
Recovered implementation PR: #1077